home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
kermit.columbia.edu
/
kermit.columbia.edu.tar
/
kermit.columbia.edu
/
newsgroups
/
misc.19950726-19950929
/
000356_news@columbia.edu_Wed Sep 13 13:36:48 1995.msg
< prev
next >
Wrap
Internet Message Format
|
1995-12-25
|
3KB
Received: from apakabar.cc.columbia.edu by watsun.cc.columbia.edu with SMTP id AA03265
(5.65c+CU/IDA-1.4.4/HLK for <kermit.misc@watsun.cc.columbia.edu>); Wed, 13 Sep 1995 22:31:36 -0400
Received: by apakabar.cc.columbia.edu id AA02103
(5.65c+CU/IDA-1.4.4/HLK for kermit.misc@watsun); Wed, 13 Sep 1995 22:31:35 -0400
Path: news.columbia.edu!sol.ctr.columbia.edu!howland.reston.ans.net!newsfeed.internetmci.com!salliemae!uunet!in1.uu.net!cs.utexas.edu!news.cs.utah.edu!cc.usu.edu!jrd
From: jrd@cc.usu.edu (Joe Doupnik)
Newsgroups: comp.protocols.kermit.misc
Subject: Re: Netware/IP and packet driver Kermit coexistence
Message-Id: <1995Sep13.193648.61242@cc.usu.edu>
Date: 13 Sep 95 19:36:48 MDT
References: <1995Sep13.140223.124158@forest>
Organization: Utah State University
Lines: 42
Apparently-To: kermit.misc@watsun.cc.columbia.edu
In article <1995Sep13.140223.124158@forest>, mrichich@forest.drew.edu (Mike Richichi, Systems Manager) writes:
> Okay, here's the issue. We have a LAN running Netware 4.1. We are
> currently using ODIPKT and MS-Kermit 3.13 to telnet to on-campus machines
> in DOS. We want to switch these machines over to Netware/IP 2.1, thus
> getting a Winsock to run Netscape, and then still be able to run MS-Kermit
> 3.13 (ideally in Windows) and still have it access tcp/ip through a packet
> driver.
>
> Now, the first thing to try is just run ODIPKT. No go--when Novell's
> TCPIP.EXE loads, it prevents ODIPKT from working, even in DOS. That's to
> be expected, though.
>
> Well, after some careful thought, lots of fun, and a few hundred machine
> reboots, I've come up with the following solution:
>
> 1) Run the packet driver for the network card (in this case, 3Com 3c509.)
> 2) Run PKTMUX and then 2 PKTDRVs.
> 3) Use PDETHER on one of the packet driver interrupts, and then load
> Novell's LSL, TCPIP, NWIP, and VLM (thus getting complete Netware
> connectivity to file servers and such.)
> 4) Kermit then takes the other packet-driver interrupt for it's tcp/ip
> connections.
> 5) Yes, this even works in Windows. I'm doing it right now, I've got my
> Kermit window covering my Netscape window, and both work simultaneously.
> There are delays in one app when the other is transmitting data, but
> again, that's to be expected.
>
>
> The big question is: Am I flirting with disaster? Is PDETHER not as good
Yes. Not as good.
> of a Netware solution as the native ODI driver for the card? Are there
> any other unforseen problems that I should know about? I'm going to hit
> it hard for a while to see if it crashes and burns.
If your site has a licensed copy of Lan WorkPlace/DOS from Novell
then component TELAPI placed on top of Novell's TCP/IP stack forms an
interface that Kermit can use, even in Windows. This is an "approved"
method to run the two products together; we think so and so does Novell.
We basically say all risks become yours when pktmux is involved.
Joe D.